[TS PBT] Project properties and search violations with USVM - #387

Summary

• project supported property domains into USVM inputs with explicit exact, approximate, unsupported, and concrete-only capabilities
• execute supported synchronous preconditions and predicates in one symbolic state according to the [TS PBT][P0] Align and simplify property execution semantics before integration #384 contract
• distinguish reached violations, bounded searches without a reached violation, unsupported execution, property errors, timeouts, engine failures, and input-resolution failures
• preserve a resolved violation candidate when another explored path ends as unsupported or fails, preferring a normal false result over an exception-shaped path
• classify TypeScript exception handlers and optional reference-valued domains as explicitly unsupported instead of reporting unsound exact support
• use the single search/guard execution path for preconditions; remove the duplicate production projector and its duplicate test path
• retain unknown-call observation while using the standard dispatcher directly

Dependency

This PR is stacked on #386 and intentionally targets caelmbleidd/issue-384-property-contract. Its base now includes the #386 review fix and ultimately starts directly from main, where #350 is already merged.

Validation

• focused capability, search, precondition, and conformance suite: 23 passed
• npm test in fast-check-adapter: 59 passed
• full :usvm-ts-pbt:test: 227 passed
• ./gradlew :usvm-ts-pbt:check :usvm-ts-pbt:installDist: passed
• ./gradlew :usvm-ts-pbt:detektMain: passed
• git diff --check: passed
• CI run 35274783868: all six jobs passed

Closes #351
Closes #352